home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20000824-20010305
/
000254_news@columbia.edu _Tue Feb 6 13:15:12 2001.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@columbia.edu>
Received: from watsun.cc.columbia.edu (watsun.cc.columbia.edu [128.59.39.2])
by fozimane.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id NAA14918
for <kermit.misc@cpunix.cc.columbia.edu>; Tue, 6 Feb 2001 13:15:11 -0500 (EST)
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id NAA00446
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 6 Feb 2001 13:15:11 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id MAA20602
for kermit.misc@watsun.cc.columbia.edu; Tue, 6 Feb 2001 12:52:48 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: fdc@columbia.edu (Frank da Cruz)
Subject: Re: Unrecognized com port
Date: 6 Feb 2001 17:52:46 GMT
Organization: Columbia University
Message-ID: <95pdle$k3n$1@newsmaster.cc.columbia.edu>
To: kermit.misc@columbia.edu
In article <fvWf6.2909$IK6.47145@news6.giganews.com>,
Steve <steve@baus-systems.com> wrote:
: Is there a list of reasons why I would get an unrecognized hardware when
: trying to use a com port from time to time? I am using 3.15 with Win98 2nd
: Edition on a PC...
:
Yes, see:
http://www.columbia.edu/kermit/msk95.html
: ... in my office and never have a problem yet a remote location
: has the exact same OS and same com drivers and they have all sorts of com
: issues.
:
You can't count on any two PCs being alike. From one day to the next, the
same manufacturer will switch parts based on whatever is cheapest that day.
The only way to be "safe" with Windows PCs is to use Windows software that
uses the native drivers for the devices on the Windows PCs. MS-DOS Kermit
can't access 32-bit drivers.
: I can not see any reason why as I have gone through the Using MSK
: in 32 bit Windows list of issues...
:
We don't even pretend to know all the issues. Modern PCs are manufactured
for Windows, and it is increasingly impossible to run 16-bit DOS software
in 32-bit Windows, especially when it needs to get at the hardware.
: ... and do not see anything that applies. I
: would have thought booting the PC to DOS would be one way around this but
: that always gives errors.
:
Does K95 work on the problem PC?
- Frank